METHODS AND/OR SYSTEMS FOR ACTIVATION AND/OR CONFIGURATION OF AN ELECTRONIC SUBSCRIBER IDENTITY MODULE (eSIM)

ABSTRACT

A device identifies device model information for the device. The device provides, to a first server device, an activation request that includes the device model information to activate an embedded subscriber identity module (eSIM) for the device. The device receives, from the first server device, an activation response that includes an eSIM profile identifier and location information that is to be used to identify eSIM profile configuration data (PCD). The device provides, to a second server device, a configuration request that includes an eSIM component identifier that identifies the eSIM of the device. The second server device is provided with the configuration request based on the location information. The device receives, from the second server device, a configuration response that includes the eSIM PCD. The device configures, by using the eSIM PCD, the eSIM with the eSIM profile.

RELATED APPLICATION

This application is a continuation of U.S. patent application Ser. No.17/249,904, entitled “METHODS AND/OR SYSTEMS FOR ACTIVATION AND/ORCONFIGURATION OF AN ELECTRONIC SUBSCRIBER IDENTITY MODULE (eSIM),” filedMar. 18, 2021, which is a continuation of U.S. patent application Ser.No. 16/670,865, entitled “METHODS AND/OR SYSTEMS FOR ACTIVATION AND/ORCONFIGURATION OF AN ELECTRONIC SUBSCRIBER IDENTITY MODULE (eSIM),” filedOct. 31, 2019 (now U.S. Pat. No. 10,966,080), for which bothapplications are incorporated herein by reference in their entirety.

BACKGROUND

A subscriber identity module (SIM) card is an integrated circuit that iscapable of securely storing an international mobile subscriber identity(IMSI) and a related key. An embedded SIM (eSIM) is a form ofprogrammable SIM that is embedded directly into a device, and that canbe remotely provisioned such that an operator can be added or removedwithout needing to physically replace the eSIM on the device.

BRIEF DESCRIPTION OF THE DRAWINGS

FIGS. 1A-IE are diagrams of one or more example implementationsdescribed herein.

FIG. 2 is a diagram of an example environment in which systems and/ormethods described herein may be implemented.

FIG. 3 is a diagram of example components of one or more devices of FIG.2.

FIGS. 4 and 5 are flowcharts of one or more example processes for remoteactivation of an embedded subscriber identity module (eSIM).

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

The following detailed description of example implementations refers tothe accompanying drawings. The same reference numbers in differentdrawings may identify the same or similar elements.

An embedded SIM (eSIM) is a form of programmable SIM that is embeddeddirectly into a user device. The eSIM can be remotely provisioned withan eSIM profile that corresponds to an account that a user has with aservice provider (e.g., a telecommunication provider, a network operator(MNO), a carrier, and/or the like).

To provision and/or identify one or more configuration items (CIs) ofthe eSIM, the user must manually submit a unique device identifier (aninternational mobile equipment identity (IMEI) and/or the like) of theuser device. For example, the user may interact with an interface of theuser device to input the unique device identifier into a field of anapplication that may be used to provision and/or identify the one ormore CIs of the eSIM. The application may be an application that isoperated by a vendor/manufacturer of an operating system of the userdevice.

However, for security and/or privacy reasons, the vendor/manufacturer ofthe operating system of the user device has prevented release of anapplication programming interface (API) that would allow a third partyapplication (e.g., a carrier application operated by the serviceprovider of the user) to assist in remotely provisioning eSIMs. Withoutthe API to allow the user device to communicate directly with a carrierplatform associated with the service provider, one or more devices usedto provision and/or identify the one or more CIs of the eSIM (the userdevice, a backend server associated with the vendor/manufacturer, othernetwork devices associated with the service provider, and/or the like)will inefficiently and/or ineffectively expend resources (e.g.,processing resources, network resources, and/or the like) whileprovisioning and/or identifying the one or more CIs of the eSIM on theuser device.

Some implementations described herein include a user equipment (UE) toperform a first set of actions (described further herein) to cause anembedded subscriber identity module (eSIM) of the UE to be remotelyactivated and configured. For example, the UE (e.g., using a carrierapplication) may identify device model information that identifies amodel of the UE and/or a version associated with the model. In thiscase, the UE may provide, to a carrier platform, an activation requestto activate the eSIM of the UE. The activation request may include thedevice model information. Additionally, the carrier platform may performa second set of actions (described further herein) that cause an eSIMprofile identifier for an eSIM profile to be assigned to the eSIM andthat cause eSIM profile configuration data for the eSIM profile (whichmay be used to configure the eSIM with the eSIM profile) to be madeavailable to the UE.

Furthermore, the UE may receive, from the carrier platform, anactivation response that includes an activation code that may be used toactivate the eSIM of the UE. The activation code may include the eSIMprofile identifier and location information that is to be used toidentify the eSIM profile configuration data. In this case, the UE mayprovide, to a remote SIM provisioning (RSP) platform, a configurationrequest that includes an eSIM component identifier that identifies theeSIM of the device. The configuration request may be provided to the RSPplatform using the location information (e.g., which may include a fullyqualified domain name (FQDN). Additionally, a data structure associatedwith the RSP platform may store the eSIM profile configuration data, andthe RSP platform may use information included in the configurationrequest to reference the data structure to identify the eSIM profileconfiguration data, and to provide the UE with a configuration responsethat includes the eSIM profile configuration data. This may allow the UEto use the eSIM profile configuration data to configure the eSIM withthe eSIM profile.

In this way, the first set of actions performed by the UE cause the eSIMto be configured with the eSIM profile. Additionally, by performingactions that cause the eSIM to be remotely provisioned without using theunique device identifier of the UE as part of an activation procedure,the UE efficiently and/or effectively utilizes resources of the UE,resources of other platforms and/or devices, and/or the like. Forexample, the UE conserves resources (e.g., processing resources, networkresources, memory resources, and/or the like) that would otherwise beused to transmit the unique device identifier over a network, reduces anumber of over the air transmissions made by devices used to configurethe eSIM (e.g., relative to an inferior solution that does not use oneor more application programming interfaces (APIs) described herein tosend and/or receive data, relative to an inferior solution that uses theunique device identifier as part of the activation procedure, and/or thelike), and/or the like. Furthermore, implementing a solution that doesnot require the unique device identifier to be sent over a network toconfigure the eSIM improves security and/or privacy concerns that mightotherwise arise were the unique device identifier to be intercepted byan unauthorized party.

FIGS. 1A-IE are diagrams of one or more example implementations 100described herein. For example, the one or more example implementations100 may include a user equipment (UE) 102, a carrier platform 104, abilling server 106, a group of data storage devices 108 that areassociated with carrier platform 104 (shown as Data Storage Device 108-1and Data Storage Device 108-2), an electronic telephone number inventory(eTNI) server 110, and a remote subscriber identity module (SIM)provisioning (RSP) platform 112. As shown in FIGS. 1A-1E. UE 102 mayperform a set actions (described herein) to cause an embedded subscriberidentity module (eSIM) of UE 102 to be remotely provisioned.

As shown in FIG. 1A, and by reference number 114, UE 102 may identifydevice model information. For example, UE 102 may identify device modelinformation that may be used to configure the eSIM of UE 102 with aneSIM profile that corresponds to an account that a user has with aservice provider.

The device model information may include information that identifies adevice model, information that identifies a version associated with thedevice model, and/or other information that generically identifies UE102. In some implementations, the device model information may exclude aunique device identifier of UE 102, such as an international mobileequipment identity (IMEI) and/or any other identifier capable ofuniquely identifying UE 102. As used herein, an identifier may uniquelyidentify a device (e.g., UE 102) if the identifier can be used toidentify the device and cannot be used to identify one or more otherdevices (e.g., including one or more other UEs 102 that share the samedevice model information).

In some implementations, before UE 102 identifies the device modelinformation, the user (e.g., a subscriber of the service provider) maypurchase UE 102 and may power on the device. For example, a displayscreen of UE 102 may, as part of a boot-up procedure, prompt the user toselect the service provider. When the user selects the service provider,the display screen may update to display a homepage or desktop of UE102. In some cases, the boot-up procedure may also cause a carrierapplication to automatically launch and be displayed via the displayscreen. In other cases, the user may manually launch the camerapplication. Additionally, the user may log into the account that theuser has with the service provider, may create a new account with theservice provider, may add one or more other users to the account, and/orthe like.

In some implementations, UE 102 may identify the device modelinformation based on a trigger condition being satisfied. The triggercondition that may cause UE 102 to identify the device model informationmay include a first indication that the boot-up procedure of UE 102 hasbeen completed, a second indication that the carrier application hasbeen launched on UE 102, a third indication that the user has loggedinto the account associated with the carrier application, and/orindications of one or more other user interface interactions and/orevents on UE 102 that may precede the configuration and/or activation ofthe eSIM of UE 102.

In some implementations, UE 102 may use the carrier application toidentify the device model information. For example, and as shown byreference number 114-1, UE 102 (e.g., using the carrier application) maydetect that a trigger condition has been satisfied. As shown byreference number 114-2, UE 102 may cause the carrier application toobtain the device model information from a device informationapplication that stores the device information locally on UE 102. Inthis case, UE 102 may cause the carrier application to provide a devicemodel information request to the device information application. Thedevice model request may be provided using a first interface (e.g., afirst application programming interface (API) and/or another type ofcommunication interface). Additionally, UE 102 may cause the deviceinformation application to reference a data structure to identify thedevice model information and may cause the device informationapplication to provide the carrier application with a device modelinformation response that includes the device model information.

Additionally, or alternatively, UE 102 may identify the device modelinformation using one or more other applications. For example, UE 102may identify the device model using a logical profile assistant (LPA)and/or another application associated with UE 102.

As shown by reference number 116, UE 102 may provide an activationrequest to carrier platform 104. For example, UE 102 may use a secondinterface (e.g., a second API and/or another type of communicationinterface) to provide carrier platform 104 with an activation request toactivate the eSIM of UE 102. The activation request may include thedevice model information of UE 102, an account identifier of the accountthat the user has with the service provider, account information for theaccount, and/or the like. Carrier platform 104 may be operated by theservice provider (e.g., and not a vendor/manufacturer of an operatingsystem of UE 102).

In the example shown, UE 102 may provide carrier platform 104 with anactivation request that includes the device model information and theaccount identifier for the account that the user has with the serviceprovider. As another example, the user may create a new account with theservice provider after powering on UE 102. In this example, the user mayinteract with an interface of the carrier application to create the newaccount, and may input account information, such as login information,address information, billing information, user preferences information,and/or the like. In this example, UE 102 may provide carrier platform104 with the account information as part of the activation request(e.g., in addition to the device model information and/or the accountidentifier).

As shown by reference number 118, carrier platform 104 may obtain, frombilling server 106, the account information for the account that theuser has with the service provider. For example, carrier platform 104may obtain the account information that may be used to configure theeSIM in a manner that provides UE 102 with access to a services packagethat is linked to the account of the user. The services package mayinclude one or more services that the user has signed up for whencreating the account, one or more services that the user has signed upfor after creating the account, one or more services that anotherauthorized user of the account has signed up for, and/or the like. Adescription of how the account information is used to configure the eSIMin a manner that provides UE 102 with access to the services package isprovided further herein.

Continuing with the example, to obtain the account information, carrierplatform 104 may provide billing server 106 with an account informationrequest that includes the account identifier of the user (and/or anyother authentication information that may be needed). This may causebilling server 106 to use the account identifier to identify the accountinformation and to provide carrier platform 104 with an accountinformation response that includes the account information. In someimplementations, carrier platform 104 may already have obtained theaccount information from UE 102 (e.g., as part of an activation request,such as when a user creates a new account while activating an eSIM of aparticular UE 102).

In this way, UE 102 causes carrier platform 104 to be provided withinformation needed to activate the eSIM (e.g., the device modelinformation and/or the account information).

As shown in FIG. 1B, and by reference number 120, carrier platform 104may obtain device stock keeping unit (SKU) information based on thedevice model information. The device SKU information may includeinformation that identifies a type of eSIM on UE 102, information thatidentifies a version of a particular type of eSIM on UE 102, and/or thelike. The eSIM may include an embedded universal integrated circuit card(EUICC), an embedded integrated circuit card (EICC), a secure element,and/or the like. While some implementations described herein refer tothe eSIM, it is to be understood that this is provided by way ofexample. In practice, one or more implementations described herein maybe implemented with a SIM card, such as a SIM card that includes a UICC,an ICC, a secure element, and/or the like.

To obtain the device SKU information, carrier platform 104 may use thedevice model information to reference a data structure associated withdata storage device 108-1. For example, the data structure may be usedto store a set of device SKU information for various types of devices.The set of device SKU information may be stored in association with acorresponding set of device model information for the various types ofdevices. In this case, carrier platform 104 may use the device modelinformation (e.g., as terms of a search query) to reference the datastructure to cause data storage device 108-1 to identify and providecarrier platform 104 with the device SKU information that corresponds tothe model that matches the model of UE 102.

As shown by reference number 122, carrier platform 104 may obtain eSIMprofile SKU information based on the device SKU information. The eSIMprofile SKU information may include an eSIM profile type identifier thatidentifies a type of eSIM profile (e.g., a type of eSIM profile may becompatible with a particular eSIM), an eSIM profile version identifierthat identifies a version of a particular eSIM profile, and/or the like.

To obtain the eSIM profile SKU information, carrier platform 104 may usethe device SKU information to search a data structure associated withdata storage device 108-2. For example, the data structure may be usedto store a set of eSIM profile SKU information for eSIM profiles thatare compatible with different types of eSIMs, different versions ofeSIMs, different hardware specifications of eSIMs, and/or the like. Theset of eSIM profile SKU information may be stored in association with acorresponding set of device SKU information for devices that includeeSIMs that are compatible with particular eSIM profiles. In this case,carrier platform 104 may use the device SKU information (e.g., as termsof a search query) to reference the data structure associated with datastorage device 108-2 to cause data storage device 108-2 to identify andprovide carrier platform 104 with the eSIM profile SKU information thatis compatible with the eSIM of UE 102 (and that corresponds to thedevice SKU information).

In this way, carrier platform 104 uses the device model information(e.g., which excludes the unique device identifier of UE 102) to obtainthe eSIM profile SKU information that identifies a type of eSIM profile(and/or a version of eSIM profile) that is compatible with the eSIM ofUE 102.

As shown in FIG. 1C, and by reference number 124, carrier platform 104may obtain an eSIM profile identifier for an eSIM profile and one ormore device identifiers associated with UE 102. For example, carrierplatform 104 may use the eSIM profile SKU information to obtain, fromeTNI server 110, an eSIM profile identifier for the eSIM profile that iscompatible with the eSIM of UE 102, and one or more device identifiersthat have been assigned to UE 102 (and/or to the account the user haswith the service provider).

The eSIM profile identifier may identify an eSIM profile that iscompatible with the eSIM of UE 102 and/or that has been assigned to theeSIM of UE 102. The eSIM profile identifier may, for example, include anICC identifier (ICCID) and/or a similar type of identifier. In theexample shown, the eSIM profile identifier may include an ICCID thatidentifies the eSIM profile. In some cases, the eSIM profile identifiermay be used as a pointer to a specific memory location used to storeeSIM profile configuration data. The one or more other deviceidentifiers may include a mobile directory number (MDN), a mobileidentification number (MIN), a mobile station identifier (MSID), and/orthe like.

In some implementations, carrier platform 104 may cause eTNI server 110to assign the eSIM profile identifier to the eSIM of UE 102 and/or toassign the one or more device identifiers to UE 102. For example,carrier platform 104 may use a third interface (e.g., a third API and/oranother type of communication interface) to provide, to eTNI server 110,the eSIM profile SKU information that identifies the type of eSIMprofile and/or the version of eSIM profile to which the eSIM of UE 102is compatible. In this case, eTNI server 110 may have access to a datastructure that associates eSIM profile identifiers for available eSIMprofiles with corresponding eSIM profile SKU information. Additionally,eTNI server 110 may use the eSIM profile SKU information received fromcarrier platform 104 to reference the data structure to identify a setof eSIM profile identifiers associated with available eSIM profiles(e.g., which are compatible with the eSIM of UE 102). In this case, eTNIserver 110 may assign an eSIM profile to the eSIM of UE 102, such thatan eSIM profile identifier for the eSIM profile is reserved specificallyfor the eSIM of UE 102. Furthermore, eTNI server 110 may reference thedata structure (or another data structure) that includes a list ofavailable device identifiers (e.g., a list of available MIDNs) and mayassign the one or more device identifiers to UE 102.

As shown by reference number 126, carrier platform 104 may interact withRSP platform 112 to cause eSIM profile configuration data to be madeavailable to (e.g., downloadable by) UE 102. For example, carrierplatform 104 may provide, to RSP platform 112, a set of instructions tocause RSP platform 112 to perform one or more actions to make eSIMprofile configuration data available to UE 102.

The set of instructions may include the eSIM profile identifier for theeSIM of UE 102, the account information for the account of the user(e.g., which may have been obtained from billing server 106, asdescribed above), a message indicating to make the eSIM profileconfiguration data available to UE 102, an eSIM profile configurationfile, and/or the like. The eSIM profile configuration file may include aset of instructions capable of providing the eSIM of UE 102 with accessto one or more services of the services package linked to the account ofthe user, instructions capable of restricting access of the eSIM to oneor more services of the services package, instructions capable ofmonitoring and/or reporting data usage associated with one or moreservices of the services package, and/or the like.

In some implementations, carrier platform 104 may cause the eSIM profileidentifier to be made available to UE 102. For example, in some cases,the eSIM profile configuration data may include only the eSIM profileidentifier. In these cases, carrier platform 104 may provide RSPplatform 112 with the eSIM provider identifier to cause RSP platform 112to make the eSIM profile identifier accessible to UE 102 via a fourthinterface (e.g., a fourth API and/or another type of communicationinterface), such as a fourth interface that permits UE 102 to downloadthe eSIM profile identifier and/or that permits carrier platform 104 toprovide UE 102 with the eSIM profile identifier.

Additionally, or alternatively, carrier platform 104 may cause the eSIMprofile configuration file to be made available to UE 102. For example,in other cases, the eSIM profile configuration data may include the eSIMprofile configuration file (e.g., in addition to the eSIM profileidentifier, instead of the eSIM profile identifier, and/or the like). Inthese cases, carrier platform 104 may provide RSP platform 112 with theeSIM profile identifier and the account information of the user.

Additionally, RSP platform 112 may process the account information toobtain and/or identify services package data for the services packagethat may be used as part of the eSIM profile configuration file. As anexample, RSP platform 112 may process the account information toidentify a price plan for the account of the user and may use the priceplan to obtain and/or identify the services package data. In thisexample, the price plan may specify that the user has purchased aparticular quantity of data. Furthermore, RSP platform 112 may obtainand/or identify, as part of the services package, a service feature thatensures that UE 102 will have access to the particular quantity of data.For example, RSP platform 112 may obtain services package data for theservices package by providing a request to a network device (e.g., ahome subscriber server (HSS), a unified data manager (UDM), and/or thelike) that stores the services package data to cause the network deviceto provide RSP platform 112 with a response that includes the servicespackage data. In this case, RSP platform 112 may configure the eSIMprofile configuration file with the services package data, such that theeSIM profile configuration file is able to provide UE 102 with access toone or more services defined by the services package. Additionally, RSPplatform 112 may cause the eSIM profile configuration file to be madeavailable to UE 102 via the fourth interface.

As shown by reference number 128, RSP platform 112 may provide carrierplatform 104 with location information that is to be used to identifythe eSIM profile configuration data. The location information mayinclude a uniform resource locator (URL), a domain name (DN), a fullyqualified domain name (FQDN), and/or the like.

As shown by reference number 130, carrier platform 104 may provide anactivation response to UE 102. For example, carrier platform 104 may usethe second interface to provide UE 102 with an activation response thatincludes the eSIM profile identifier, the one or more deviceidentifiers, the location information that is to be used to identify theeSIM profile configuration data, and/or the like. In the example shown,carrier platform 104 may provide UE 102 with the eSIM profileidentifier, the MDN of UE 102, and a FQDN that may permit UE 102 toobtain the eSIM profile configuration data (as described furtherherein).

In this way, UE 102 is provided with an activation response thatincludes information that may be used to activate the eSIM of UE 102(e.g., without UE 102 having to include a unique device identifier inthe activation request, without having to provide the unique deviceidentifier to carrier platform 104, and/or the like).

As shown in FIG. 1D, and by reference number 132. UE 102 may identify aneSIM component identifier. For example, UE 102 (e.g., using a logicalprofile assistant (LPA) and/or another software element of UE 102) mayidentify an eSIM component identifier by referencing a data structureassociated with UE 102. The eSIM component identifier may be used toidentify the eSIM of UE 102 and may include an eICCID, an eUICCID,and/or the like. In the example shown, where the eSIM profile identifieris an ICCID that identifies the eSIM profile, an eICCID or an eUICCID(shown as eID) may be used as the eSIM component identifier to identifythe eSIM of UE 102.

As shown by reference number 134, UE 102 may provide RSP platform 112with a configuration request. For example, UE 102 may provide aconfiguration request to RSP platform 112 via a fifth interface. Thefifth interface may include a fifth API and/or another type ofcommunication interface. For example, the fifth interface may include asecure interface, an interface released as part of a specificationassociated with a global organization that establishes industrystandards that the service provider must abide by (e.g., an ES9interface and/or a similar type of interface), and/or the like. Theconfiguration request may include the eSIM component identifier. In someimplementations, UE 102 may use the location information (e.g., theFQDN) to provide RSP platform 112 with the configuration request (e.g.,by visiting a website hosted by RSP platform 112). In the example shown,UE 102 may provide RSP platform 112 with a configuration request thatincludes an eICCID (shown as eID).

As shown by reference number 136, RSP platform 112 may identify the eSIMprofile configuration data. For example, RSP platform 112 may use theeSIM profile identifier (e.g., the ICCID) to identify the eSIM profileconfiguration data. The ICCID may have been previously provided to RSPplatform 112 (see, e.g., FIG. 1C). The eSIM profile configuration datamay be stored in association with a corresponding eSIM profileidentifier. In this case, RSP platform 112 may verify that UE 102 ispermitted to access the eSIM profile configuration data by comparing theeSIM profile identifier with the corresponding eSIM profile identifierthat is stored in association with the eSIM profile configuration data.

As shown by reference number 138, RSP platform 112 may provide UE 102with a configuration response. For example, RSP platform 112 mayprovide, to UE 102 and via the fifth interface, a configuration responsethat includes the eSIM profile configuration data.

In some implementations, UE 102 may obtain the eSIM profileconfiguration data (e.g., without a configuration request-configurationresponse interaction with RSP platform 112). For example, UE 102 may usethe FQDN to access a website that allows UE 102 to download the eSIMprofile configuration data. In this case, UE 102 may input credentialinformation (e.g., the account information of the user, the eSIM profileidentifier, the eSIM component identifier, and/or the like) to access apage of the website that permits UE 102 to download the eSIM profileconfiguration data.

As shown by reference number 140, UE 102 may configure the eSIM with theeSIM profile using the eSIM profile configuration data. In some cases,such as when the eSIM profile configuration data excludes the eSIMconfiguration file, UE 102 may configure the eSIM such that a set ofconnection parameters (e.g., a set of UICC parameters, which may includethe eSIM profile identifier of the eSIM) may be used as part of aconnection procedure when UE 102 is to access one or more services via anetwork. For example, UE 102 may store a set of UICC connectionparameters, which may include the eSIM profile identifier of the eSIM,such that the set of UICC connection parameters may be used as part ofan attachment procedure that allows UE 102 to connect to a network, suchas a fourth generation (4G) network, a fifth generation (5G) network,and/or the like.

In other cases, such as when the eSIM profile configuration dataincludes the eSIM profile configuration file, UE 102 may execute theeSIM profile configuration file to configure the eSIM of UE 102. Byconfiguring the eSIM, UE 102 may be able to access the services packagethat includes the one or more services that are linked to the account ofthe user.

In this way, UE 102 configures the eSIM with the assigned eSIM profile(e.g., without UE 102 having to include the unique device identifier inthe activation request, without having to provide the unique deviceidentifier to carrier platform 104, and/or the like).

As shown in FIG. 1E, and by reference number 142, RSP platform 112 mayprovide the eSIM component identifier to carrier platform 104. Forexample, RSP platform 112 may provide the eSIM component identifier tocarrier platform 104 as part of a notification that indicates that theeSIM profile has been activated on the eSIM of UE 102.

As shown by reference number 144, carrier platform 104 may identify theunique device identifier of UE 102 based on the eSIM componentidentifier. For example, carrier platform 104 may identify the uniquedevice identifier of UE 102 by using the eSIM component identifier toreference a data structure that associates the eSIM component identifierand the unique device identifier of UE 102. The unique device identifiermay include an international mobile equipment identity (IMEI) and/or anyother identifier capable of uniquely identifying UE 102.

As shown by reference number 146, carrier platform 104 may update one ormore records associated with the account of the user. For example,carrier platform 104 may update contents of another data structure thatis used to store one or more records associated with the account of theuser. In this case, carrier platform 104 may use the other datastructure to associate the unique device identifier, the eSIM componentidentifier, the eSIM profile identifier, the one or more other uniquedevice identifiers (e.g., the MDN), and/or the like.

In some implementations, one or more implementations described hereinmay be applied to a number sharing situation, where UE 102 and one ormore companion UEs 102 share the same MDN. For example, the user maypurchase a second UE 102 that includes a second eSIM. In this case, thesecond UE 102 (and/or UE 102) may perform one or more actions that aredescribed herein as being performed by UE 102. As an example, UE 102 may(e.g., using a camera component) capture device model information of thesecond UE 102 (e.g., which may be visible on a bar code or on part ofthe second UE 102). In this example, UE 102 may provide carrier platform104 with an activation request and may receive, from carrier platform104, an activation response that includes a second eSIM profileidentifier for a second eSIM profile that is compatible with a secondeSIM of the second UE 102, the MDN of UE 102 (e.g., which will be sharedwith the second UE 102), and location information that is to be used toidentify eSIM profile configuration data for the second eSIM profile.Additionally, UE 102 may provide RSP platform 112 with a configurationrequest and receive, from RSP platform 112, a configuration responsethat includes the eSIM profile configuration data for the second eSIMprofile. This may allow UE 102 to provide the second UE 102 with theeSIM profile configuration for the second eSIM profile to allow thesecond UE 102 to configure the second eSIM with the second eSIM profile.

In this way, UE 102 (and/or one or more other devices described herein)causes the eSIM to be configured with the eSIM profile. By causing theeSIM to be configured with the eSIM profile using the one or moreinterfaces (e.g., APIs) described herein, UE 102 efficiently and/oreffectively utilizes resources of UE 102 and/or resources of otherplatforms and/or devices, such as by conserving resources (e.g.,processing resources, network resources, memory resources, and/or thelike) that would otherwise be used to transmit the unique deviceidentifier of UE 102 over a network, by reducing a number of over theair transmissions made by devices used to configure the eSIM (e.g.,relative to an inferior solution that does not use one or moreapplication programming interfaces (APIs) described herein to sendand/or receive data, relative to an inferior solution that uses theunique device identifier as part of the activation procedure, and/or thelike), and/or the like.

As indicated above, FIGS. 1A-1E are provided as one or more examples.Other examples can differ from what is described with regard to FIGS.1A-IE. For example, there may be additional devices and/or networks,fewer devices and/or networks, different devices and/or networks, ordifferently arranged devices and/or networks than those shown in FIGS.1A-1E. Furthermore, two or more devices shown in FIGS. 1A-IE may beimplemented within a single device, or a single device shown in FIGS.1A-IE may be implemented as multiple and/or distributed devices.Additionally, or alternatively, a set of devices (e.g., one or moredevices) included in the one or more example implementations 100 mayperform one or more functions described as being performed by anotherset of devices included in the one or more example implementations 100.

FIG. 2 is a diagram of an example environment 200 in which systemsand/or methods, described herein, may be implemented. As shown in FIG.2, environment 200 may include a user equipment (UE) 210, a billingserver 220, a carrier platform 230 hosted within a cloud computingenvironment 240, a data storage device 250, a remote subscriber identitymodule (SIM) provisioning (RSP) platform 260, an electronic telephonenumber inventory (eTNI) platform 270, and/or a network 280. Devices ofenvironment 200 may interconnect via wired connections, wirelessconnections, or a combination of wired and wireless connections.

UE 210 includes one or more devices capable of receiving, storing,generating, processing, and/or providing information associated withactivating and/or configuring an embedded SIM (eSIM). For example, UE210 may include a wireless communication device, a radiotelephone, apersonal communications system (PCS) terminal (e.g., that may combine acellular radiotelephone with data processing and data communicationscapabilities), a smart phone, a laptop computer, a tablet computer, apersonal gaming system, a machine-to-machine (M2M) device, an internetof things (IoT) device, and/or a similar device.

In some implementations, UE 210 may include an eSIM. As used herein, aneSIM may include an embedded universal integrated circuit card (EUICC),and embedded integrated circuit card (EICC), a secure element, a virtualSIM, and/or the like. Additionally, or alternatively, UE 210 may includea device information application (e.g., an application capable ofgenerating and/or identifying device model information of UE 210), acarrier application, and/or the like. The carrier application mayinclude an application capable of interfacing UE 210 with carrierplatform 230, an application capable of registering a user for one ormore services, an application capable of capturing and/or displayingaccount information of a user, and/or the like.

In some implementations, UE 210 may have access to one or moreinterfaces of a group of interfaces described in connection with FIGS.1A-1E. For example, UE 210 may use a first interface to allow a carrierapplication of UE 210 to communicate with a device informationapplication of UE 210, may use a second interface to provide anactivation request to carrier platform 230, may use the second interfaceto receive an activation response from carrier platform 230, may use athird interface to obtain an eSIM profile identifier (e.g., an ICCID),may use a fourth interface to provide RSP platform 260 with aconfiguration request, and may use the fourth interface to receive aconfiguration response from RSP platform 260.

Billing server 220 includes one or more devices capable of receiving,storing, generating, processing, and/or providing information associatedwith an account of a user. For example, billing server 220 may include aserver device or a group of server devices. In some implementations,billing server 220 may receive new account information for the accountof the user. In some implementations, billing server 220 may have accessto a data structure that is used to store account information for theaccount of the user. In some implementations, billing server 220 mayprovide the account information to carrier platform 230.

Carrier platform 230 includes one or more devices capable of receiving,storing, generating, processing, and/or providing information associatedwith activating and/or configuring an eSIM. For example, carrierplatform 230 may include a server device (e.g., a host server, a webserver, an application server, etc.), a data center device, or a similardevice.

In some implementations, carrier platform 230 may have access to one ormore of the group of interfaces described in connection with FIGS.1A-1E. For example, carrier platform 230 may use the second interface toreceive the activation request from UE 210, may use the third interfaceto obtain an eSIM profile identifier and one or more device identifiersfrom eTNI platform 270, may use a fifth interface to communicate withRSP platform 260 to cause the eSIM profile configuration data to beaccessible to UE 210. In some implementations, two or more interfaces,of the group of interfaces, may be implemented as a single interface.

In some implementations, as shown, carrier platform 230 may be hosted incloud computing environment 240. While implementations described hereindescribe carrier platform 230 as being hosted in cloud computingenvironment 240, in some implementations, carrier platform 230 might notbe cloud-based (i.e., may be implemented outside of a cloud computingenvironment) or may be partially cloud-based.

Cloud computing environment 240 includes an environment that hostscarrier platform 230. Cloud computing environment 240 may providecomputation, software, data access, storage, etc. services that do notrequire end-user knowledge of a physical location and configuration ofsystem(s) and/or device(s) that hosts carrier platform 230. As shown,cloud computing environment 240 may include a group of computingresources 235 (referred to collectively as “computing resources 235” andindividually as “computing resource 235”).

Computing resource 235 includes one or more personal computers,workstation computers, server devices, or another type of computationand/or communication device. In some implementations, computing resource235 may host carrier platform 230. The cloud resources may includecompute instances executing in computing resource 235, storage devicesprovided in computing resource 235, data transfer devices provided bycomputing resource 235, and/or the like. In some implementations,computing resource 235 may communicate with other computing resources235 via wired connections, wireless connections, or a combination ofwired and wireless connections.

As further shown in FIG. 2, computing resource 235 may include a groupof cloud resources, such as one or more applications (“APPs”) 235-1, oneor more virtual machines (“VMs”) 235-2, virtualized storage (“VSs”)235-3, one or more hypervisors (“HYPs”) 235-4, and/or the like.

Application 235-1 may include one or more software applications that maybe provided to or accessed by UE 210, billing server 220, data storagedevice 250, RSP platform 260, and/or eTNI platform 270. Application235-1 may eliminate a need to install and execute the softwareapplications on these devices. For example, application 235-1 mayinclude software associated with carrier platform 230 and/or any othersoftware capable of being provided via cloud computing environment 240.In some implementations, one application 235-1 may send/receiveinformation to/from one or more other applications 235-1, via virtualmachine 235-2.

Virtual machine 235-2 may include a software implementation of a machine(e.g., a computer) that executes programs like a physical machine.Virtual machine 235-2 may be either a system virtual machine or aprocess virtual machine, depending upon use and degree of correspondenceto any real machine by virtual machine 235-2. A system virtual machinemay provide a complete system platform that supports execution of acomplete operating system (“OS”). A process virtual machine may executea single program and may support a single process. In someimplementations, virtual machine 235-2 may execute on behalf of anotherdevice (e.g., UE 210, billing server 220, data storage device 250, RSPplatform 260, and/or eTNI platform 270), and may manage infrastructureof cloud computing environment 240, such as data management,synchronization, or long-duration data transfers.

Virtualized storage 235-3 may include one or more storage systems and/orone or more devices that use virtualization techniques within thestorage systems or devices of computing resource 235. In someimplementations, within the context of a storage system, types ofvirtualizations may include block virtualization and filevirtualization. Block virtualization may refer to abstraction (orseparation) of logical storage from physical storage so that the storagesystem may be accessed without regard to physical storage orheterogeneous structure. The separation may permit administrators of thestorage system flexibility in how the administrators manage storage forend users. File virtualization may eliminate dependencies between dataaccessed at a file level and a location where files are physicallystored. This may enable optimization of storage use, serverconsolidation, and/or performance of non-disruptive file migrations.

Hypervisor 235-4 may provide hardware virtualization techniques thatallow multiple operating systems (e.g., “guest operating systems”) toexecute concurrently on a host computer, such as computing resource 235.Hypervisor 235-4 may present a virtual operating platform to the guestoperating systems and may manage the execution of the guest operatingsystems. Multiple instances of a variety of operating systems may sharevirtualized hardware resources.

Data storage device 250 includes one or more devices capable ofreceiving, storing, generating, processing, and/or providing trafficassociated with activating and/or configuring an eSIM. For example, datastorage device 250 may include a server device or a group of serverdevices. In some implementations, data storage device 250 may use a datastructure to store device stock keeping unit (SKU) information inassociation with device model information and with eSIM profile SKUinformation. In some implementations, a first data storage device 250may use a data structure to store the device SKU information inassociation with the device model information. Additionally, oralternatively, a second data storage device 250 may use a data structureto store the device SKU information in association with the eSIM profileSKU information.

RSP platform 260 includes one or more devices capable of receiving,storing, generating, processing, and/or providing information associatedwith activating and/or configuring an eSIM. For example, RSP platform260 may include a server device or a group of server devices. In someimplementations, RSP platform 260 may have access to one or more of thegroup of interfaces described in connection with FIGS. 1A-IE. Forexample, RSP platform 260 may use the fourth interface to communicatewith UE 210 to provide UE 210 with the eSIM profile configuration dataand may use the fifth interface to communicate with carrier platform 230to cause the eSIM profile configuration data to be accessible to UE 210.

eTNI platform 270 includes one or more devices capable of receiving,generating, processing, and/or providing traffic associated withactivating and/or configuring an eSIM. For example, eTNI platform 270may include a server device or a group of server devices. In someimplementations, eTNI platform 270 may use one or more data structuresto store available MDNs, available eSIM profile identifiers, and/or thelike. In some implementations, another platform or server (other thaneTNI platform 270) may be used to store the available MDNs, theavailable eSIM profile identifiers, and/or the like. For example, aplatform or server associated with a cloud service provider may be usedto store the available MDNs, the available eSIM profile identifiers,and/or the like.

Network 280 includes one or more wired and/or wireless networks. Forexample, network 280 may include a telecommunications network (e.g., afifth generation (5G) network, a fourth generation (4G) network, such asan LTE network, a 3G network, a code division multiple access (CDMA)network, etc.), a public land mobile network (PLMN), a wireless localarea network (e.g., a Wi-Fi network), a local area network (LAN), a widearea network (WAN), a metropolitan area network (MAN), a telephonenetwork (e.g., the Public Switched Telephone Network (PSTN)), a privatenetwork, an ad hoc network, an intranet, the Internet, a fiberoptic-based network, a cloud computing network, a packet switchednetwork (PSN), a multiprotocol label switching (MPLS) network, and/or acombination of these or other types of networks.

The number and arrangement of devices and networks shown in FIG. 2 areprovided as one or more examples. In practice, there may be additionaldevices and/or networks, fewer devices and/or networks, differentdevices and/or networks, or differently arranged devices and/or networksthan those shown in FIG. 2. Furthermore, two or more devices shown inFIG. 2 may be implemented within a single device, or a single deviceshown in FIG. 2 may be implemented as multiple, distributed devices.Additionally, or alternatively, a set of devices (e.g., one or moredevices) of environment 200 may perform one or more functions describedas being performed by another set of devices of environment 200.

FIG. 3 is a diagram of example components of a device 300. Device 300may correspond to UE 210, billing server 220, carrier platform 230, datastorage device 250, RSP platform 260, and/or eTNI platform 270. In someimplementations, UE 210, billing server 220, carrier platform 230, datastorage device 250, RSP platform 260, and/or eTNI platform 270 mayinclude one or more devices 300 and/or one or more components of device300. As shown in FIG. 3, device 300 may include a bus 310, a processor320, a memory 330, a storage component 340, an input component 350, anoutput component 360, and a communication interface 370.

Bus 310 includes a component that permits communication among multiplecomponents of device 300. Processor 320 is implemented in hardware,firmware, and/or a combination of hardware and software. Processor 320includes a central processing unit (CPU), a graphics processing unit(GPU), an accelerated processing unit (APU), a microprocessor, amicrocontroller, a digital signal processor (DSP), a field-programmablegate array (FPGA), an application-specific integrated circuit (ASIC),and/or another type of processing component. In some implementations,processor 320 includes one or more processors capable of beingprogrammed to perform a function. Memory 330 includes a random accessmemory (RAM), a read only memory (ROM), and/or another type of dynamicor static storage device (e.g., a flash memory, a magnetic memory,and/or an optical memory) that stores information and/or instructionsfor use by processor 320.

Storage component 340 stores information and/or software related to theoperation and use of device 300. For example, storage component 340 mayinclude a hard disk (e.g., a magnetic disk, an optical disk, and/or amagneto-optic disk), a solid state drive (SSD), a compact disc (CD), adigital versatile disc (DVD), a floppy disk, a cartridge, a magnetictape, and/or another type of non-transitory computer-readable medium,along with a corresponding drive.

Input component 350 includes a component that permits device 300 toreceive information, such as via user input (e.g., a touch screendisplay, a keyboard, a keypad, a mouse, a button, a switch, and/or amicrophone). Additionally, or alternatively, input component 350 mayinclude a component for determining location (e.g., a global positioningsystem (GPS) component) and/or a sensor (e.g., an accelerometer, agyroscope, an actuator, another type of positional or environmentalsensor, and/or the like). Output component 360 includes a component thatprovides output information from device 300 (via, e.g., a display, aspeaker, a haptic feedback component, an audio or visual indicator,and/or the like).

Communication interface 370 includes a transceiver-like component (e.g.,a transceiver, a separate receiver, a separate transmitter, and/or thelike) that enables device 300 to communicate with other devices, such asvia a wired connection, a wireless connection, or a combination of wiredand wireless connections. Communication interface 370 may permit device300 to receive information from another device and/or provideinformation to another device. For example, communication interface 370may include an Ethernet interface, an optical interface, a coaxialinterface, an infrared interface, a radio frequency (RF) interface, auniversal serial bus (USB) interface, a wireless local area networkinterface, a cellular network interface, and/or the like.

Device 300 may perform one or more processes described herein. Device300 may perform these processes based on processor 320 executingsoftware instructions stored by a non-transitory computer-readablemedium, such as memory 330 and/or storage component 340. As used herein,the term “computer-readable medium” refers to a non-transitory memorydevice. A memory device includes memory space within a single physicalstorage device or memory space spread across multiple physical storagedevices.

Software instructions may be read into memory 330 and/or storagecomponent 340 from another computer-readable medium or from anotherdevice via communication interface 370. When executed, softwareinstructions stored in memory 330 and/or storage component 340 may causeprocessor 320 to perform one or more processes described herein.Additionally, or alternatively, hardware circuitry may be used in placeof or in combination with software instructions to perform one or moreprocesses described herein. Thus, implementations described herein arenot limited to any specific combination of hardware circuitry andsoftware.

The number and arrangement of components shown in FIG. 3 are provided asan example. In practice, device 300 may include additional components,fewer components, different components, or differently arrangedcomponents than those shown in FIG. 3. Additionally, or alternatively, aset of components (e.g., one or more components) of device 300 mayperform one or more functions described as being performed by anotherset of components of device 300.

FIG. 4 is a flow chart of an example process 400 for methods and/orsystems for remote activation of an embedded subscriber identity module(eSIM). In some implementations, one or more process blocks of FIG. 4may be performed by a device (e.g., a user equipment (UE) 210). In someimplementations, one or more process blocks of FIG. 4 may be performedby another device or a group of devices separate from or including thedevice, such as a billing server (e.g., billing server 220), a carrierplatform (e.g., carrier platform 230), a data storage device (e.g., datastorage device 250), a remote SIM provisioning (RSP) platform (e.g., RSPplatform 260), an electronic telephone number inventory (eTNI) platform(e.g., eTNI platform 270), and/or the like.

As shown in FIG. 4, process 400 may include identifying, by a device,device model information for the device (block 410). For example, thedevice (e.g., UE 210, using processor 320, memory 330, storage component340, input component 350, communication interface 370, and/or the like)may identify device model information for the device, as describedabove.

In some implementations, the device model information may exclude aunique identifier of the device. For example, the device modelinformation may exclude an international mobile equipment identity(IMEI) of the device. In some implementations, the device modelinformation may generically identify the device. In someimplementations, the device model information may include at least oneof: information that identifies a device model, or information thatidentifies a version associated with the device model.

In some implementations, the device may determine that a triggercondition has been satisfied. In some implementations, the device mayidentify the device model information based on determining that thetrigger condition has been satisfied. The trigger condition may includeat least one of: a first indication that a boot-up procedure of thedevice has been completed, a second indication that a carrierapplication has been launched on the device, a third indication that auser has logged into an account that the user has with a serviceprovider.

In some implementations, the device may cause a carrier application touse an application programming interface (API) to provide a device modelinformation request to another application to cause the otherapplication to reference a data stmcture to identify the device modelinformation. The carrier application and the other application may bothbe executed on the device.

As further shown in FIG. 4, process 400 may include providing, to afirst server device, an activation request to activate an embeddedsubscriber identity module (eSIM) for the device, wherein the activationrequest includes the device model information, and wherein providing theactivation request to the first server device permits the first serverdevice to perform a set of actions that cause an eSIM profile identifierfor an eSIM profile to be assigned to the eSIM and that cause eSIMprofile configuration data for the eSIM profile to be made available tothe device (block 420). For example, the device (e.g., UE 210, usingprocessor 320, memory 330, storage component 340, output component 360,communication interface 370, and/or the like) may provide, to a firstserver device (e.g., carrier platform 230), an activation request toactivate an eSIM for the device, as described above. In someimplementations, the activation request may include the device modelinformation. In some implementations, providing the activation requestto the first server device may permit the first server device to performa set of actions that cause an eSIM profile identifier for an eSIMprofile to be assigned to the eSIM and that cause eSIM profileconfiguration data for the eSIM profile to be made available to thedevice.

In some implementations, the device may provide, as part of theactivation request, the device model information and an accountidentifier for an account associated with a user. The device modelinformation may be used by the first server device to cause the eSIMprofile identifier to be assigned to the eSIM. The account identifiermay be used by the first server device to cause the eSIM profileconfiguration data for the eSIM profile to be made available to thedevice.

In some implementations, the device may receive, based on an interactionwith a user interface of the device, account information associated withan account of a user. In some implementations, when providing theactivation request, the device may provide the account information tothe first server device as part of the activation request. In someimplementations, providing the account information to the first serverdevice may permit the first server device to use the account informationto obtain services data (e.g., services package data) that is to beincluded in the eSIM profile configuration data and that identifies aset of services that are linked to the account of the user.

As further shown in FIG. 4, process 400 may include receiving, from thefirst server device, an activation response that includes an activationcode with the eSIM profile identifier and location information that isto be used to identify the eSIM profile configuration data (block 430).For example, the device (e.g., UE 210, using processor 320, memory 330,storage component 340, input component 350, communication interface 370,and/or the like) may receive, from the first server device, anactivation response that includes an activation code with the eSIMprofile identifier and location information that is to be used toidentify the eSIM profile configuration data, as described above.

In some implementations, the location information may include a fullyqualified domain name (FQDN). In some implementations, the locationinformation may include domain information (e.g., that includes a domainname).

As further shown in FIG. 4, process 400 may include providing, to asecond server device, a configuration request that includes an eSIMcomponent identifier that identifies the eSIM of the device, wherein theconfiguration request is provided to the second server device based onthe location information that is to be used to identify the eSIM profileconfiguration data (block 440). For example, the device (e.g., UE 210,using processor 320, memory 330, storage component 340, output component360, communication interface 370, and/or the like) may provide, to asecond server device (e.g., RSP platform 260), a configuration requestthat includes an eSIM component identifier that identifies the eSIM ofthe device, as described above. In some implementations, the device mayidentify the eSIM component identifier that is to be included in theconfiguration request by referencing a data structure local to thedevice. In some implementations, the configuration request may beprovided to the second server device based on the location informationthat is to be used to identify the eSIM profile configuration data. Forexample, the device may use a FQDN to visit a website that is used todisplay and/or store profile data for users, which may allow the secondserver device to use the eSIM profile identifier (e.g., an ICCID) toidentify the eSIM.

As further shown in FIG. 4, process 400 may include receiving, from thesecond server device, a configuration response that includes the eSIMprofile configuration data (block 450). For example, the device (e.g.,UE 210, using processor 320, memory 330, storage component 340, inputcomponent 350, communication interface 370, and/or the like) mayreceive, from the second server device, a configuration response thatincludes the eSIM profile configuration data, as described above.

As further shown in FIG. 4, process 400 may include configuring, byusing the eSIM profile configuration data, the eSIM with the eSIMprofile (block 460). For example, the device (e.g., UE 210, usingprocessor 320, memory 330, storage component 340, and/or the like) mayconfigure, by using the eSIM profile configuration data, the eSIM withthe eSIM profile, as described above.

Although FIG. 4 shows example blocks of process 400, in someimplementations, process 400 may include additional blocks, fewerblocks, different blocks, or differently arranged blocks than thosedepicted in FIG. 4. Additionally, or alternatively, two or more of theblocks of process 400 may be performed in parallel.

FIG. 5 is a data flow diagram of an example process 500 for methodsand/or systems for remote activation of an embedded subscriber identitymodule (eSIM). As shown in FIG. 5, and by reference number 505, a userequipment (UE) may power up and a user may interact with the UE tochoose a cellular service carrier. As shown by reference number 510, acarrier application of the UE may identify device model information ofthe UE by making a device model application programming interface (API)call to a device information application of the UE. As shown byreference number 515, the device information application of the UE mayprovide the device model information to the carrier application (e.g.,based on device model API call). As shown by reference number 520, auser may input account information into an interface of the carrierapplication.

As shown by reference number 525, the carrier application of the UE mayprovide, to a carrier platform, an eSIM activation request that includesthe device model information and/or the account information of the user.In this case, the carrier platform may identify device SKU information,may select matching eSIM SKU information, and may select an integratedcircuit card identifier (ICCID) and a mobile directory number (MDN) forthe UE.

As shown by reference number 530, the carrier platform may interact witha remote SIM provisioning (RSP) platform to set the ICCID to adownloadable state. In some implementations, the RSP platform may, whilesetting the ICCID to a downloadable state, generate a matching ID. As anexample, the RSP platform may generate a matching ID that is representedby the string KTHAMX2EIC4KSULD.

As shown by reference number 535, the carrier platform may provide afully qualified domain name (FQDN) and/or the matching ID to the carrierapplication of the UE. For example, the carrier platform may provide anactivation code that includes the FQDN and the matching ID. As aspecific example, the carrier platform may provide the carrierapplication of the UE with the following activation code:LPA:1$xyz.prod.ondemandconnectivity.com$ KTHAMX2EIC4KSULD. In thisexample, the FQDN may be the text located before the second dollar sign(LPA:1$xyz.prod.ondemandconnectivity.com) and the match ID may be thetext after the second dollar sign (THAMX2EIC4KSULD).

As shown by reference number 540, the carrier application of the UE mayprovide, to a logical profile assistant (LPA) of the UE, the FQDN and/orthe matching ID. As shown by reference number 545, the LPA of the UE mayinteract with the RSP platform to query for the eSIM profile. Forexample, the LPA of the UE may use the FQDN to identify a website hostedby the RSP platform and may query for the eSIM profile by providing theRSP platform with the matching ID and/or an embedded identifier (eID)that identifies the eSIM of the UE. As shown in FIG. 5, the UE may,based on the query, download the eSIM profile for the eSIM. In thiscase, the UE may configure the eSIM with the eSIM profile to activateone or more services of the cellular service provider. As shown byreference number 550, the RSP platform may notify the carrier platformthat the download succeeded and may provide the carrier platform withthe eID. This may allow the carrier platform to use the eID to locate aunique device identifier of the UE (e.g., an international mobileequipment identity (IMEI)) and to associate the eID, the unique deviceidentifier, the ICCID, and MDN, and/or the like.

Although FIG. 5 shows example operations of process 500, in someimplementations, process 500 may include additional operations, feweroperations, different operations, or differently arranged operationsthan those depicted in FIG. 5. Additionally, or alternatively, two ormore of the operations of process 500 may be performed in parallel.

The foregoing disclosure provides illustration and description but isnot intended to be exhaustive or to limit the implementations to theprecise form disclosed. Modifications and variations may be made inlight of the above disclosure or may be acquired from practice of theimplementations.

As used herein, the term “component” is intended to be broadly construedas hardware, firmware, or a combination of hardware and software.

Some implementations are described herein in connection with thresholds.As used herein, satisfying a threshold may, depending on the context,refer to a value being greater than the threshold, more than thethreshold, higher than the threshold, greater than or equal to thethreshold, less than the threshold, fewer than the threshold, lower thanthe threshold, less than or equal to the threshold, equal to thethreshold, etc., depending on the context.

Certain user interfaces have been described herein and/or shown in thefigures. A user interface may include a graphical user interface, anon-graphical user interface, a text-based user interface, and/or thelike. A user interface may provide information for display. In someimplementations, a user may interact with the information, such as byproviding input via an input component of a device that provides theuser interface for display. In some implementations, a user interfacemay be configurable by a device and/or a user (e.g., a user may changethe size of the user interface, information provided via the userinterface, a position of information provided via the user interface,etc.). Additionally, or alternatively, a user interface may bepre-configured to a standard configuration, a specific configurationbased on a type of device on which the user interface is displayed,and/or a set of configurations based on capabilities and/orspecifications associated with a device on which the user interface isdisplayed.

To the extent the aforementioned implementations collect, store, oremploy personal information of individuals, it should be understood thatsuch information shall be used in accordance with all applicable lawsconcerning protection of personal information. Additionally, thecollection, storage, and use of such information can be subject toconsent of the individual to such activity, for example, through wellknown “opt-in” or “opt-out” processes as can be appropriate for thesituation and type of information. Storage and use of personalinformation can be in an appropriately secure manner reflective of thetype of information, for example, through various encryption andanonymization techniques for particularly sensitive information.

It will be apparent that systems and/or methods described herein may beimplemented in different forms of hardware, firmware, and/or acombination of hardware and software. The actual specialized controlhardware or software code used to implement these systems and/or methodsis not limiting of the implementations. Thus, the operation and behaviorof the systems and/or methods are described herein without reference tospecific software code—it being understood that software and hardwarecan be used to implement the systems and/or methods based on thedescription herein.

Even though particular combinations of features are recited in theclaims and/or disclosed in the specification, these combinations are notintended to limit the disclosure of various implementations. In fact,many of these features may be combined in ways not specifically recitedin the claims and/or disclosed in the specification. Although eachdependent claim listed below may directly depend on only one claim, thedisclosure of various implementations includes each dependent claim incombination with every other claim in the claim set.

No element, act, or instruction used herein should be construed ascritical or essential unless explicitly described as such. Also, as usedherein, the articles “a” and “an” are intended to include one or moreitems, and may be used interchangeably with “one or more.” Further, asused herein, the article “the” is intended to include one or more itemsreferenced in connection with the article “the” and may be usedinterchangeably with “the one or more.” Furthermore, as used herein, theterm “set” is intended to include one or more items (e.g., relateditems, unrelated items, a combination of related and unrelated items,etc.), and may be used interchangeably with “one or more.” Where onlyone item is intended, the phrase “only one” or similar language is used.Also, as used herein, the terms “has,” “have,” “having,” or the like areintended to be open-ended terms. Further, the phrase “based on” isintended to mean “based, at least in part, on” unless explicitly statedotherwise. Also, as used herein, the term “or” is intended to beinclusive when used in a series and may be used interchangeably with“and/or,” unless explicitly stated otherwise (e.g., if used incombination with “either” or “only one of”).

1-20. (canceled)
 21. A method, comprising: providing, by the device andto a first server device, an activation request to activate an embeddedsubscriber identity module (eSIM) of the device, wherein the activationrequest includes device model information for the device, and whereinthe device model information does not uniquely identify the device;receiving, by the device and from the first server device, an activationresponse that includes an eSIM profile identifier assigned to the deviceand location information associated with a second server device;determining, by the device, an eSIM component identifier associated withthe device and identifying the eSIM of the device; sending, by thedevice and to the second server device using the location information, aconfiguration request that includes the eSIM component identifier thatidentifies the eSIM of the device, wherein the configuration requestincludes the eSIM profile identifier; receiving, by the device and fromthe second server device, a configuration response that includes eSIMprofile configuration data; and configuring, by the device, the eSIM ofthe device using the eSIM profile configuration data.
 22. The method ofclaim 21, wherein the device model information includes at least one of:information that identifies a device model, or information thatidentifies a version associated with the device model.
 23. The method ofclaim 21, further comprising: determining that a trigger condition hasbeen satisfied, wherein the trigger condition includes at least one of:a first indication that a boot-up procedure of the device has beencompleted, a second indication that a carrier application has beenlaunched on the device, or a third indication that a user has loggedinto an account that the user has with a service provider; andidentifying the device model information based on determining that thetrigger condition has been satisfied.
 24. The method of claim 21,further comprising: causing a carrier application to use an applicationprogramming interface (API) to provide a device model informationrequest to another application to cause the other application toreference a data structure to identify the device model information,wherein the carrier application and the other application are both beingexecuted on the device.
 25. The method of claim 21, wherein the locationinformation includes a fully qualified domain name (FQDN).
 26. Themethod of claim 21, wherein providing the activation request comprises:providing, as part of the activation request, the device modelinformation and an account identifier for an account associated with auser.
 27. The method of claim 21, wherein the activation responseincludes a device identifier assigned to the device.
 28. The method ofclaim 21, wherein the eSIM profile identifier is an Integrated CircuitCard Identifier (ICCID).
 29. The method of claim 21, wherein the eSIMcomponent identifier is an eUICC Id (EID).
 30. The method of claim 21,wherein at least one of sending the configuration request or configuringthe eSIM of the device using the eSIM profile configuration data isperformed by a Local Profile Assistant (LPA) executing on the device.31. The method of claim 21, wherein the second server device is a RemoteSIM Provisioning (RSP) platform.
 32. A method comprising: receiving,from a device and at a remote platform, an activation request toactivate an embedded subscriber identity module (eSIM) of the device,wherein the activation request includes device model information for thedevice, the device model information for the device not uniquelyidentifying the device; determining an eSIM profile type using thedevice model information; assigning an Integrated Circuit CardIdentifier (ICCID) for an eSIM profile to be assigned to the eSIM, theassigning based on the eSIM profile type; obtaining eSIM profileconfiguration data from a remote data platform; providing an activationresponse to the device, the activation response including the ICCID;receiving, from the device, a configuration request that includes aneSIM component identifier that identifies the eSIM of the device,wherein the configuration request further includes the ICCID; providinga configuration response to the device, the configuration responseincluding the eSIM profile configuration data to allow the device toactivate the eSIM of the device.
 33. The method of claim 32, wherein theactivation request includes an account identifier associated with a userof the device.
 34. The method of claim 32, further including assigning adevice identifier for the UE, and wherein providing the activationresponse includes providing the device identifier.
 35. The method ofclaim 32, wherein the remote data platform is at least one of an HSS orUDM.
 36. The method of claim 32, further comprising: obtaining a uniqueidentifier of the device using the eSIM component identifier; andproviding the unique identifier of the device to the remote dataplatform.
 37. The method of claim 36, wherein the unique identifier isan International Mobile Equipment Identifier (IMEI) of the device. 38.The method of claim 32, wherein the activation response includeslocation information which can be used by the device to send theconfiguration request.
 39. The method of claim 32, wherein obtainingeSIM profile configuration data from the remote data platform includesobtaining services package data associated with the device, andconfiguring the eSIM profile configuration data with the servicespackage data.
 40. The method of claim 32, wherein receiving theactivation request, determining the eSIM profile type, assigning theICCID and providing the activation response are performed by a firstplatform; receiving the configuration request and providing theconfiguration response are performed by a second platform separate fromthe first platform; and the method further comprises: sending the ICCIDfrom the first platform to the second platform; and sending the eSIMcomponent identifier from the second platform to the first platform.